![]() |
Pong Conferences - OPENING QUESTION: What remaining tasks do you have? Make a list and be specific! LEARNING TARGET: I will crate a "to-do" check list for remaining issues on Pong. I will work on stepping through my check list during today's class. WORDS O' THE DAY:
WORK O' THE DAY: PONG SPECS are HERE How did the: --- please click here to see the "Ask" and "Tell" function blocks go yesterday? That looked to me to be a POWERFUL tool for us? Let's discuss. ═══════════════════════════ Please make sure to step through your check list. That means: 1) Making sure that you DO spend a significant amount of time working on a problem. Try different approaches, do research and OF COURSE, brainstorm with your colleagues. Spending 5 - 10 minutes on a problem may seem like a lot of time. It AIN'T. Also, nothing is worse then telling your program manager that you have examined EVERY SINGLE ASPECT OF THE PROBLEM AND IT JUST CAN'T BE DONE. Only to have your program manager ponder the problem for a few micro-seconds and provide you with an answer that you probably should have come up with (trust me on this!) Be humble. Now, having said that, the flip side can be also really important. That is by way of saying don't spend TOO much time on one check-list item. It is REALLY easy in programming to hyper-focus on one task to the exclusion of all else. That's not productive. That is hacking. Hacking is not productive.
You'll be surprised how stepping away from a problem for a while can make a huge difference in solving a problem. I've hacked (yes, hacked!) on problems for hours and hours. Stepped away for a few hours and then nailed the problem in a few minutes when I came back. That is very common. DO NOT indulge your inner hacker. What is the path through all of this? Please confer with your team. Let's discuss! |